Meta data enhanced television programming

ABSTRACT

A variety of meta data based enhancements to media content viewing are described, including making meta data corresponding to media content available for user searching and using meta data to identify highlight portions of the media content so that only the highlight portions need to be stored. Additionally, comments made to media content can be shared with other viewers of the content, even when viewing the content at different times and even when viewing different versions of the content. Furthermore, a synchronization point can be established for the media content and used by the client systems as a common reference location. In addition, advertisements for media content can be rendered based on how much time has been spent rendering the media content, as well as the amount of a fee paid by the user of the client system.

CROSS REFERENCE TO RELATED APPLICATION

This application is a divisional application of U.S. patent applicationSer. No. 09/775,393, filed on Jan. 21, 2001, and entitled “META DATAENHANCED TELEVISION PROGRAMMING,” which is incorporated herein in itsentirety by reference.

TECHNICAL FIELD

This invention relates to storage and rendering of media content, andmore particularly to meta data enhanced television programming.

BACKGROUND OF THE INVENTION

Televisions have become commonplace in homes throughout many countriesand increasingly throughout the world. Viewing of television programminghas traditionally taken the form of either “live” viewing (that is,viewing as the television program is being broadcast) or time delayedviewing. Video cassette recorders (VCRs) have been used for many yearsto record programs for delayed viewing. More recently, however, digitalvideo recorders (DVRs) have become available that allow televisionprograms to be stored digitally on a hard disk for delayed viewing.

DVRs have allowed some enhancements to be made to television programviewing, such as a pause feature to pause the playback of the televisionprogram while it is being broadcast (with the remainder of the programbeing stored to the hard disk for later viewing). However, theseenhancements remain in the general category of time delayed viewing—theviewer is able to record and thus delay viewing of the remainder of theprogram until a later time.

In addition to viewing television programs, other media have been usedto distribute programming. Video cassettes have been used for many yearsto distribute movies and other programming for playback in VCRs.Additionally, other media such as Digital Versatile Disks (DVDs) arebecoming increasingly popular for distributing movies and otherprogramming. While DVDs are typically capable of providing higherresolution images and higher quality audio than video cassettes, andallow for faster random accessing of portions of the programming, DVDplayers typically do not provide much more in the way of enhancedfunctionality than is available from VCRs.

Despite these advances in recording devices and audio/video storagetechnology, there remains a need to expand on the television viewingenhancements available to users. The invention described below addressesthese needs, providing meta data enhanced television programming.

SUMMARY OF THE INVENTION

Meta data enhanced television programming is described herein.

In accordance with one aspect, meta data associated with media contentis made available for user-searching. The user can enter search criteriaand have rendered to him or her one or more portions of thecorresponding media content that match the search criteria.

In accordance with another aspect, meta data associated with mediacontent is used to conserve storage space used for storing the mediacontent. Highlight portions of the media content are identified in themeta data and only those highlight portions of the media content aresaved. The identification can be performed as the media content isreceived, resulting in the non-highlight portions not being saved, orall of the media content may be initially saved and the non-highlightportions subsequently deleted.

In accordance with another aspect, meta data associated with mediacontent is used to identify highlight portions of the media content.Different meta data sources may be available from which differenthighlight portions can be identified. For example, the media content maybe a baseball game and different meta data sources may identifydifferent portions of the baseball game as highlights (e.g., there maybe a pay-for-use service from which identified highlights can bereceived for a fee, and there may be a free service from which otheridentified highlights can be received). The user can then view thehighlight portions, as identified by one or more of the meta datasources, thereby allowing the user to watch the baseball game for ashorter amount of time that is necessary to watch the entire game but atthe same view the most important parts of the baseball game.

In accordance with another aspect, comments to media content can beentered and saved by multiple different viewers of the content. Thesecomments are then made available to subsequent viewers when viewing thecontent. The comments can be added regardless of whether the viewersview the content concurrently or at different times, and regardless ofwhether the viewers view the same version of the content (e.g., from theserver or DVD) or different versions (e.g., some viewing a version froma server with others viewing a version from a DVD).

In accordance with another aspect, a synchronization point isestablished for media content. This synchronization point is after thebeginning of the media content and is used by client systems as a commonreference location to identify offsets for comments and/or other metadata.

In accordance with another aspect, advertisements for media content arerendered based on how much time has been spent viewing the mediacontent. If greater than a threshold amount of time elapses without anadvertisement being rendered, one or more advertisements are rendered onthe client system. The number of advertisements can also vary, based onthe amount of a fee paid by the user of the client system.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the figures of the accompanying drawings. The same numbersare used throughout the figures to reference like components and/orfeatures.

FIG. 1 shows an exemplary content distribution and viewing system inaccordance with certain embodiments of the invention.

FIG. 2 is a block diagram illustrating an exemplary media contentrendering system in accordance with certain embodiments of theinvention.

FIG. 3 illustrates an exemplary meta data server such as may be used inaccordance with certain embodiments of the invention.

FIG. 4 is a flowchart illustrating an exemplary process for usingsynchronization points in accordance with certain embodiments of theinvention.

FIG. 5 is a block diagram illustrating a multi-user media contentcommenting environment in accordance with certain embodiments of theinvention.

FIG. 6 is a flowchart illustrating an exemplary process for usingcomments in accordance with certain embodiments of the invention.

FIG. 7 is a flowchart illustrating an exemplary process for meta databased browsing and storage in accordance with certain embodiments of theinvention.

FIG. 8 is a flowchart illustrating an exemplary process for renderingadvertisements in accordance with certain embodiments of the invention.

FIG. 9 illustrates an example of a suitable operating environment inwhich the invention may be implemented.

DETAILED DESCRIPTION

FIG. 1 shows an exemplary content distribution and viewing system 100 inaccordance with certain embodiments of the invention. Entertainmentsystem 100 includes a client media content rendering system 102 having adisplay device including a viewing area 104 and a receiver 106. Mediacontent rendering system 102 represents any of a wide variety of devicesfor rendering video and/or audio content as well as other types of mediacontent, such as text, graphics, animation, etc. System 102 can be, forexample, a personal computer, a gaming console and television, othertypes of computing devices, etc. Receiver 106 is connected to receiveand render media content from multiple different programming sources.Receiver 106 may also include a storage device (e.g., magnetic and/oroptical, disks) to store received media content (also referred to asprogramming) prior to rendering on system 102. Media content can berendered individually or alternatively multiple types of media contentcan be rendered concurrently (e.g., a multimedia presentation).Additionally, media content can be delivered to receiver 106 in itsentirety (e.g., an entire program) before rendering begins, oralternatively rendering may begin prior to receiving the entirety of thecontent (e.g., streaming media content). Receiver 106 may be combinedwith a display device into a single component (e.g., a personal computeror television), or alternatively receiver 106 and display device may beseparate components.

FIG. 1 shows several different physical sources of programming,including a terrestrial television broadcasting system 108 which canbroadcast analog or digital signals that are received by antenna 110; asatellite broadcasting system 112 which can transmit analog or digitalsignals that are received by satellite dish 114; a cable signaltransmitter 116 which can transmit analog or digital signals that arereceived via cable 118; and networked media content servers 120 and 122which can each transmit digital signals that are received via acommunications network 124. System 102 can be coupled to network 124 viaany of a wide variety of conventional components (e.g., by a modem,router, etc.). Both analog and digital signals can include audio, video,and/or data content. Other programming sources might also be used indifferent situations, including interactive television systems.

In one implementation, analog signals are encoded upon receipt by thereceiver 106 in order to put the signals into a computer friendlydigital form. Alternatively, some or all analog signals may be renderedwithout conversion to digital form.

Additional network(s) may also be involved in the distribution ofprogramming to system 102. By way of example, system 102 may be includedas part of a home network (not shown), with the programming being storedat a server (not shown) prior to transmission to system 102.

Typically, audio, video, and any other content for a particular program(or portion thereof) will be transmitted from the same source (e.g., allof the content for a particular movie may be received from cabletransmitter 116). Alternatively, the audio, video, and any other contentfor a program may be transmitted from multiple sources (e.g., the audioand video content may be received from cable transmitter 116, while textand animation content is received from content server 120).

System 102 is also optionally coupled to meta data server 126 vianetwork 124. Meta data server 126 stores meta data corresponding tocontent available from one of the various programming sources. Meta datais generally data that describes other data, and in the illustratedexample the meta data describes its corresponding media content. Themeta data can be, for example, comments, annotations, highlightidentifications (e.g., identified portions of a baseball game), and soforth as discussed in more detail below. Meta data servers may bestandalone servers such as server 126, or alternatively coupled directlyto a content server such as meta data server 130 coupled to contentserver 122.

Communications network 124 can be any of a variety of networks,including a public network (e.g., the Internet), as well as a privatenetwork (e.g., a corporate local area network (LAN) or wide area network(WAN)), or combinations thereof. Communications network 124 can beimplemented in any of a variety of different manners, including wiredand/or wireless communications media.

Communication over network 124 can be carried out using any of a widevariety of communications protocols. In one implementation, network 124,system 122, and servers 120, 122, and 126 support the World Wide Web.The World Wide Web (also referred to as simply the “web”) is acollection of documents (also referred to as “web pages”) that users canview or otherwise render and which typically include links to one ormore other pages that the user can access. Communications using theWorld Wide Web can be in accordance with the Hypertext Transfer Protocol(HTTP), in which World Wide Web pages are written in a markup language,such as the Hypertext Markup Language (HTML) or the eXtensible MarkupLanguage (XML).

FIG. 2 is a block diagram illustrating an exemplary media contentrendering system 102 in accordance with certain embodiments of theinvention. Media content to be played back on client media contentrendering system 102 is received at a demultiplexer 160, which separatesthe media content into separate content streams and forwards the contentstreams to appropriate rendering components to render the content. Inthe illustrated example, demultiplexer 160 separates the media contentinto an audio stream that is forwarded to audio renderer 162 and a videostream that is forwarded to video renderer 164. Audio renderer 162 playsthe audio (e.g., via speakers) of system 102, while video renderer 164plays the video data (e.g., via a display device). Meta data that is tobe rendered to a user may also be received at demultiplexer 160 andforwarded to meta data renderer 163 for rendering. The operation of metadata renderer 163 varies depending on the type of meta data (e.g., audiometa data may be played via speakers while video data may be played viathe display device). Alternatively, rather than receiving combinedcontent that is separated into multiple streams, client system 102 mayreceive content separately (e.g., as separate streams) that can be inputto the appropriate renderer(s) directly without being demultiplexed bysystem 102.

The media content can be received at demultiplexer 160 from an externalsource(s) 166 or alternatively a local storage device(s) 168. Externalsource 166 can be any of a wide variety of conventional programmingsources, such as those sources discussed above with reference to FIG. 1,a computing device, a digital audio and/or video recorder, a videocamera, etc. Local mass storage device 168 can be a writeable device(e.g., a writeable DVD or magnetic hard disk) that receives mediacontent from another source (e.g., external source 166) and stores itlocally for subsequent viewing, or alternatively a read-only device(e.g., non-writeable DVD). Additionally, storage device 168 may includefixed storage media (e.g., a typical magnetic hard disk drive) and/orremovable storage media (e.g., a DVD).

Client system 102 also includes a meta data controller 176 coupled toreceive meta data from an external meta data server 178 (e.g., server126 or 130 of FIG. 1). Additionally, some distributed media (e.g., DVDs)may include meta data for the media content stored on the media,allowing controller 176 to receive meta data from the media (e.g.,storage device 168). All of the meta data corresponding to particularmedia content may be obtained from the same source (e.g., the sameserver), or alternatively multiple different sources (e.g., multipleservers, a local storage device and a remote server, etc.).

The meta data received by controller 176 can include any of a widevariety of information regarding the corresponding media content. Theexact nature of the meta data will vary, depending on the correspondingmedia content and the intended or desired use of the meta data. Examplesof meta data include index information (identifying particular temporallocations of the media content for particular subjects), segmentationinformation (classifying temporal portions of the media content),highlight information (which portions are highlight portions, a relativeimportance of portions, etc.), comments or annotations, etc. The metadata can include data that is intended for rendering to the user, orthat which is not intended for rendering to the user. If the meta datais to be rendered, controller 176 communicates the meta data to renderer163 either indirectly via demultiplexer 160 or alternatively directly.

The meta data associated with particular media content can be receivedin a variety of different manners. In one implementation, when mediacontent is requested from a content source, the content sourcecommunicates with the meta data server to obtain the meta dataassociated with the requested media content. The meta data server canthen communicate the meta data directly to the requesting client, oralternatively to the requesting client via the media content source.

In another implementation, meta data controller 176 communicates arequest to the meta data server for meta data associated with identifiedmedia content. If multiple servers 178 exist, controller 176 may need tobe informed of which one to access for the meta data (e.g., a defaultserver associated with the client system 102, an indication given fromthe source of the media content, an indication embedded in the mediacontent, etc.). Controller 176 passes an identifier of the media contentto server 178 that uniquely identifies the content, such as a title andproducer (or release date) of the content, an assigned globally uniqueID (GUID), etc. If any meta data is available for the media content,that meta data is returned from server 178 to controller 176.

The meta data may be communicated to controller 176 as a group andcontroller 176 determine when the meta data is to be rendered (if atall), such as by comparing the temporal location(s) of the meta data tothe current location of the media content being rendered. Alternatively,the meta data may be communicated to controller 176 as it is needed andrendered or otherwise used upon receipt (e.g., comment server 178 may bein communication with the source of the media content to know thecurrent location of the media content being communicated to clientsystem 102, or demultiplexer 160 to know the current location of themedia content being presented to renderers 162 and 164).

Meta data controller 176 can optionally store the received meta data atclient system 102. The meta data can be stored, for example, in volatilestorage (e.g., system RAM) or nonvolatile storage (e.g., mass storagedevice 168).

Meta data can be generated during the broadcast of a program (e.g.,during a “live” event), or alternatively afterwards (e.g., the programmay be stored in its entirety and meta data added based on the storedversion). Meta data can be made available from any of a wide variety ofsources. Examples of such sources include third-party professionals(e.g., individuals or groups that index or identify highlights based ontheir expertise and optionally charge individuals for access to the metadata), broadcasters (e.g., the source of the media content), “regular”viewers (e.g., a group of viewers may be able to vote (e.g., a scalefrom 1-10) on how important particular portions of the content are andstore the compiled votes as meta data), or machine-generated (e.g.,automatic identification of which portions are more important, such asbased on the presence of excited speech, bright lighting, etc.).

In certain embodiments, meta data controller 176 also makes the metadata available for user-searching. The meta data available foruser-searching can be intended for rendering to the user oralternatively not for rendering to the user (e.g., intended only forsearching). Client system 102 also includes zero or more input devices170, via which the user can input search criteria to controller 176.Upon receipt of the search criteria, controller 176 compares the searchcriteria with the meta data. Exact matches may be required, oralternatively well-known wildcards may be used in the matching process.

If controller 176 identifies any matches between the search criteria andthe meta data, appropriate action is taken. This appropriate action canvary, and can be a default course of action, can be a course of actionpreviously identified by the user, can be a prompt to the user for whichof multiple actions to take, etc. In one implementation, two differentcourses of action can be taken: the user can jump to the location in themedia content that corresponds to the match, or the user can play backone or more portions of the media content that correspond to the match.

By way of example, particular media content may be a baseball game andthe meta data may include various aspects about the game andcorresponding temporal locations in the game, such as the temporallocations for each inning, each hit, each homerun, each stolen base,each player at bat, each pitcher, etc. The user can then subsequentlysearch the meta data with particular search criteria, such as aparticular player's name. The user can then request playback of allportions of the media content with which the particular player's name isassociated (e.g., each temporal range when the identified player is atbat).

Meta data controller 176 can further be used to conserve storage spacein system 102. For example, storage device 168 has a limited amount ofstorage space, and situations may arise where the user of client system102 has requested that more content be stored than there is availablestorage space. Such situations can be resolved by limiting the mediacontent that is stored in storage device 168 based on the correspondingmeta data. Meta data can include an indication of which portions of themedia content are “highlights”—that is, which portions are perceived orexpected to be perceived as the most important portions. This can be avariable amount (e.g., the user may request that the highlights comprise20% of the media content, resulting in the 20% most important (orexpected to be most important) portions being identified).Alternatively, this can be a fixed amount (e.g., the author(s) of themeta data may simply identify which portions are highlights and whichportions are not highlights without regard for how much of the mediacontent is identified as highlights).

Meta data controller 176 uses these highlight indications to determinewhich portions of the media content are stored on storage device 168.Only those portions which are highlights are kept on device 168—otherportions are not. In one implementation, controller 176 performs theanalysis “on the fly”—as the portions are received controller 176 checksthe associated meta data to determine if they are highlights, storesthem to device 168 if they are highlights, and drops them if they arenot highlights. In another implementation, controller 176 performs theanalysis after the fact. All of the media content (or at least some ofthe media content) is initially saved to device 168. After the mediacontent is saved, controller 176 analyzes the associated meta data todetermine which portions are highlights and deletes those portions thatare not highlights from device 168.

When maintaining only certain portions of the media content rather thanall of the content, care should be taken to ensure that a proper recordof the offsets into the original media content are maintained. Forexample, if the highlights of a ten-minute program are only minutes fivethrough seven, then a record should be kept that thirty seconds into thehighlight portion is actually five minutes and thirty seconds into themedia content. This allows consistency to be maintained for commentsand/or other meta data. Maintaining such a record can be accomplished,for example, by maintaining a mapping from the offsets into thehighlight portions to the offsets into the original media content.

Another example of meta data is comments or annotations that are addedby users to which the corresponding media content is rendered. Meta datacontroller 176 optionally allows a user to input, via input device(s)170, comments regarding media content being rendered at system 102.These comments can be in any of a variety of formats, such as textual(via a keyboard), audio (via a microphone), etc.

When a comment is received from a user of system 102, meta datacontroller 176 records the comment as well as an indication of alocation of the media content that the comment corresponds to. The mediacontent has a timeline associated with it so that temporal locations ofthe content can be identified. The timeline can directly identify time(e.g., a number of minutes and seconds) or alternatively indirectlyidentify time (e.g., a number of “units”, where units can be any desiredmeasure such as data frames, number of bytes, etc.). Comments cancorrespond to a single temporal location of the media content oralternatively a range of temporal locations. The location(s) that acomment corresponds to can be identified in a variety of manners, suchas by the user manually identifying a particular location(s), based onwhen the user selects a particular command (e.g., “add comment”, “createcomment”, etc.), etc.

Upon receipt of a comment, meta data controller 176 records the temporallocation(s) of the comment (referenced to a synchronization point, asdiscussed in more detail below) and either saves the comment locally orforwards the comment to a remote meta data server. Controller 176 mayforward comments to the remote meta data server as they are received, oralternatively store multiple comments locally before forwarding themultiple comments to the remote server. Controller 176 forwards thecomments it receives to a remote meta data server 178. Server 178 storesthe received comments and makes them available to other viewers. Suchother viewers can be playing the same media content at the same time(thereby allowing a discussion regarding the media content to evolve)and/or at a subsequent time (thereby allowing a subsequent viewer(s) tobenefit from a previous discussion). Alternatively, such other viewersmay retrieve and render the comments separately from the media content(e.g., someone who has already watched the content may desire to skimthrough the comments but not watch the media content again).

Alternatively, some comments may be stored locally at client 102, suchas on mass storage device 168. Examples of comments that a user maydesire to store locally are private or personal comments for particularcontent. For example, a user may add comments to one of his or her homemovies and have those comments stored locally on device 168.

Meta data controller 176 also manages the rendering of comments onclient system 102. When the user is rendering media content, meta datacontroller 176 accesses remote server 178 to determine whether there areany comments corresponding to the media content.

In the illustrated example, controller 176 forwards comments todemultiplexer 160 which communicates the comments to renderer 163.Alternatively, controller 176 may forward the comments directly torenderer 163.

FIG. 3 illustrates an exemplary meta data server such as may be used inaccordance with certain embodiments of the invention. FIG. 3 isdiscussed primarily with reference to meta data that includes comments,although other types of meta data may also be included. Server 200includes a comment handler 202 and a storage device 204. Comment handler202 manages the receipt of comments from and the transmission ofcomments to client systems (e.g., client system 102 of FIG. 2). Storagedevice 204 maintains comments for multiple (n) comment sets, eachcorresponding to particular media content (e.g., a particular televisionprogram, a particular movie, etc.). Each comment set includes anidentifier of the media content corresponding to the comment set as wellas the comments themselves. Alternatively, a separate record of themedia content identifiers may be maintained with identifiers of (e.g.,pointers to) the associated comments.

When a new comment is received from a client system, comment handler 202receives the new comment, identifies (based on the media identifiers)the appropriate comment set, and adds the comment to the appropriatecomment set. Handler 202 also stores, as part of the comment, anidentifier of the temporal location of the media content correspondingto the comment, and optionally an identifier of the user that made thecomment. Similarly, when a client system requests comments correspondingto particular media content, comment handler 202 identifies theappropriate comment set based on the media content identifier andforwards the comments in the comment set to the requesting clientsystem.

Comment handler 202 may also limit access to particular comment sets. Acoordinating user (the identity of which may vary per comment set) mayoptionally identify a group of one or more individuals that are allowedto access a particular comment set. The individuals can be identified inany of a variety of manners, such as by network address of theircorresponding client systems, by user name, by user ID and password,etc. Only those individuals identified by the coordinator are allowed toaccess the comments in the comment set. In such situations, when commenthandler 202 receives a request for comments, comment handler 202 furtherverifies that the requestor is entitled to access the comment set. Ifso, then the comments are returned to the requestor; if not, thecomments are not returned to the requestor. Similarly, only theidentified users are able to add comments to the set. Any commentsreceived from a user that is not entitled to add comments are ignored byhandler 202. Note also that different groups may be identified forcomment sets, such as one group identifying users allowed to read thecomments and another group identifying users allowed to add newcomments.

An example of limiting access to comment sets' is in the classroomsetting. A teacher may assign students to watch particular media contentand add comments about it. The teacher communicates with comment handler202 to limit comments to be viewed and added only by the students in theclass, thereby limiting the discussion (in the comments) to thosestudents that are in the class.

Server 200 may also store other types of meta data. For example, commenthandler 202 may also manage the storage and retrieval of other types ofmeta data, such as highlight indications. These highlight indicationscan be stored in a manner analogous to the storage of comments. Forexample, highlight indications from different sources (such as one ormore subscription sources/services and one or more freesources/services) can be stored with an identifier of the media contentcorresponding to the highlight indications. Handler 202 may restrict theretrieval of such highlight indications (e.g., a user id and passwordmay be required for the user to prove that he or she is authorized toaccess highlight indications from a subscription service, or access tosome of the highlight indications may be prohibited until payment isreceived (e.g., charge to a credit card or other account)).

Returning to FIG. 2, different versions of media content can beavailable for rendering to the user of client system 102. Differentversions of media content refer to different storage and/or presentationformats. Examples of different versions of media content include: DVD,VHS, DV (Digital Video), ASF (Advanced Streaming Format), MPEG-2 (MovingPictures Experts Group-2), MPEG-4, etc. These different versions ofmedia content can have the same meta data (e.g., comments by viewers)consolidated so that one viewer can benefit from the meta data even if adifferent version of the content is being viewed than the version thatwas viewed when the meta data was created.

In order to make meta data corresponding to media content more useful,it is important to have the correct location of the meta data identified(e.g., so a comment played back by different users is played back at thesame time with reference to the corresponding media content).Unfortunately, different versions of the media content can be set updifferently. For example, one version of a movie may have playback ofthe first title screen five seconds after the “beginning” of the version(the first data of the stored version), while another may have playbackof the first title screen ten seconds after its beginning. Thus, usingthe beginning of the media content as a reference point for meta datawould be confusing, because thirty seconds into one of the versionscorresponds to different media content being rendered than thirtyseconds into the other version.

This problem can be resolved by establishing a synchronization pointthat all meta data is referenced to. Thus, rather than referring to metadata as being offset from the beginning of the media content, the metadata is referred to as being offset from the synchronization point. Thesynchronization point may be, for example, three seconds or twelveseconds after the beginning of the media content that is rendered (e.g.,after the first title screen of a movie).

The synchronization point can be identified in a variety of differentmanners. In one implementation, the source of the media contentcommunicates an indication of the synchronization point, which can be,for example, a data byte (or packet or some other unit) including a flagidentifying the point, a watermark in one or more audio and/or videoframes that can be recognized by the client but is not perceptible to auser when rendered, a particular audio and/or video frame(s) havingcertain characteristics (e.g., 30% of the pixels are orange, 28% of thepixels are green, and 16% of the pixels are purple), etc. Thesynchronization point identifier can be embedded in the media content(e.g., an invisible or inaudible flag or watermark, or a particularframe having certain characteristics), or alternatively thesynchronization point identifier can be inserted into the media contentstream by the source (e.g., an indication may be provided during thevertical blanking interval (VBI)). Alternatively, the synchronizationpoint identifier can be inserted into a different stream, such as oneavailable via a different channel that the client can tune to.

In another implementation, the synchronization point for media contentis agreed upon (or simply stated, such as by the author of the content)and distributed, publicly posted, or otherwise made available to thoseinterested in it. Such an agreed upon or stated synchronization pointcan be, for example, a frame of audio or video that includes particulardata, such as the first frame of a title page (e.g., a page identifyingthe producer of the film, the title of the film, etc.).

Additionally, one or more reference points may also be used to identifythe synchronization point. For example, situations can arise where theclient system does not receive the identifier of the synchronizationpoint, such as if the synchronization point is fifteen seconds after thestart of the version but the client system does not actually contact theremote source and start receiving the media content until ten minutesafter it started. Reference points are additional identifiers of thesynchronization point, indicating, for example, how long ago thesynchronization point was. Reference points can be identified in any ofthe same manners as synchronization points, and can be established atregular and/or irregular intervals of the media content. For example, aparticular television broadcast may have a reference point one minuteafter the start of the broadcast that identifies the synchronizationpoint as having occurred thirty seconds ago.

FIG. 4 is a flowchart illustrating an exemplary process for usingsynchronization points in accordance with certain embodiments of theinvention. The process of FIG. 4 is carried out by a client system 102,and may be implemented in software.

Initially, a request to render media content is received, such as from auser (act 212). Such a request could be, for example, entry of anidentifier of the content, selection of a particular channel, insertionof a DVD, etc. The requested media content is accessed (act 214) andrendered (act 216). The appropriate synchronization point is identifiedin the media content (act 218) and is used as the reference location forthe media content (act 220). Reference points to the synchronizationpoint may also optionally be identified (act 222), in order to verifythe synchronization point identified in act 218, in the eventidentification of the synchronization point in act 218 fails, etc.

By identifying a common synchronization point to be used by all of theclient systems rendering particular media content, meta data can beadded by users that refer to the same temporal locations of all versionsof the media content. FIG. 5 is a block diagram illustrating amulti-user media content commenting environment in accordance withcertain embodiments of the invention. In the network environment 230,multiple client systems 232, 234, and 236 are coupled to network 124.Each of the client systems 232-236 may be, for example, a client system102 of FIG. 2. In the illustrated example, the users of each of clientsystems 232-236 can access the same media content but different versionsof the content. For example, the user of client system 232 may accessthe media content from a local storage device 238 (e.g., DVD), while theuser of client system 234 may access the media content from contentserver 240 and the user of client system 236 may access the mediacontent from content server 242.

The users of client systems 232-236 can access their respective versionsof the media content at the same time, different times, overlappingtimes, etc. However, regardless of the time that the media content isaccessed, each client system 232-236 accesses meta data server 244 toobtain any meta data (e.g., comments) from previous (or concurrent)users. Similarly, any comments or other meta data added by the users ofclients 232-236 are added to server 244 and are played for anysubsequent (or concurrent users). Thus, server 244 provides aconsolidation location for all of the viewers of the media contentregardless of which version the viewers are playing.

FIG. 6 is a flowchart illustrating an exemplary process for usingcomments in accordance with certain embodiments of the invention. Theprocess of FIG. 6 is carried out by a client system 102, and may beimplemented in software.

Initially, a request to render media content is received, such as from auser (act 270). Such a request could be, for example, entry of anidentifier of the content, selection of a particular channel, insertionof a DVD, etc. The requested media content is accessed (act 272) as arecomments associated with the requested media content (act 274). Therequested media content and comments are then rendered (act 276).Additional comments may also be received from a user during rendering(act 278), and these comments are returned to the source of the comments(e.g., a comment server) for the media content (act 280) for storage.

FIG. 7 is a flowchart illustrating an exemplary process for meta databased browsing and storage in accordance with certain embodiments of theinvention. The process of FIG. 7 is carried out by a client system 102,and may be implemented in software.

Initially, media content is received at the client system, such as inresponse to a user request (act 300). Such a request could be, forexample, entry of an identifier of the content, selection of aparticular channel, insertion of a DVD, etc. Meta data corresponding tothe media content is also received (act 302) and made available for usersearching (act 304). Additionally, highlighted portions of the mediacontent are optionally identified based on the meta data (act 306) andonly those highlighted portions are saved (act 308), thereby conservinglocal storage space.

Returning to FIG. 2, client system 102 also includes an advertisementcontroller 180. Advertisement controller 180 monitors the rendered media(e.g., as communicated by demultiplexer 160, or as rendered by renderers162, 163, and/or 164) and determines when it is appropriate to renderadvertisements or commercials. The advertisements to be rendered can bereceived from an external source (e.g., source 166) or a local source(e.g., storage device 168). Client system 102 includes an advertisementcontroller to compensate for situations where advertisements may beskipped, such as when advertisements are not identified as highlightsand thus are not saved on storage device 168. Additionally, some clients102 may allow the user to fast forward fifteen or thirty seconds (commonamounts of time for advertisements) and thus easily skip overadvertisements.

In the illustrated example, advertisement controller 180 relies on beingable to know what media content is being rendered. Controller 180 canobtain such information in a variety of manners. In one implementation,the source of the content communicates an identifier of the mediacontent (e.g., a title and producer, a serial number uniquelyidentifying the content, etc.) to client system 102. This identifier maybe communicated multiple times during delivery of the media content,accounting for situations where a user begins viewing content after ithas begun (e.g., half-way through a movie). In another implementation,controller 180 accesses an electronic programming guide (e.g., storedlocally or remotely) and, based on the channel the client system istuned to, the current time, and the location of the client system (e.g.,based on zip code input by the user), and looks up an identifier of themedia content from the electronic programming guide based on thisinformation.

Advertisement controller 180 has access to information identifying whereadvertisements are embedded in media content, if at all. Thisinformation can be included in the media content (e.g., a flag signalingan advertisement), may be inherent in the media content (e.g., tenminutes after the synchronization point, eighteen minutes after thesynchronization point, etc.), may be identified in the meta data, etc.Advertisement controller 180 is also programmed with a threshold amountof time to use in determining when advertisements are to be rendered.This threshold amount of time can be programmed in any of a variety ofmanners, such as in response to a command from a source of the mediacontent (this could be incorporated into the meta data associated withthe media content, embedded within the media content itself, the subjectof a separate communication, etc.). The threshold amount of time isestablished so that not greater than a certain amount of time passesbetween advertisements. The threshold amount of time can vary bycontent, and can optionally vary by portion of the content (e.g., acontent broadcaster may prefer to have the first thirty minutes of amovie to be advertisement-free in order to get viewers hooked, thendecrease the threshold (e.g., to fifteen minutes) towards the end of themovie).

Advertisement controller 180 monitors the media content being renderedand checks whether an advertisement has been rendered. An advertisementthat is skipped over is not treated as being rendered. If anadvertisement(s) is rendered then controller 180 resets a counter of thetime since the last advertisement to zero. The total number ofadvertisements or cumulative duration of the advertisements renderedthat are required in order to reset the time since the lastadvertisement can be programmed in controller 180, such as in responseto a command from a source of the media content (analogous to theprogramming of the threshold amount of time discussed above). Thisnumber or duration can vary by content, and may also vary by portion ofthe content.

If the threshold amount of time elapses without an advertisement,controller 180 stops the rendering of the media content and inserts oneor more advertisements. Once the inserted advertisements are rendered,the amount of time since the last advertisement is reset to zero andrendering of the media content continues until the threshold amount oftime again elapses. Advertisement controller 180 monitors only the timethat the media content is actually being rendered—if playback of themedia content is paused, so too is the counting of elapsed time paused.

The advertisements rendered after the threshold amount of time haselapsed can be obtained from a local source (e.g., storage device 168)or alternatively a remote source (e.g., a remote server, which may bethe same as or different from the source of the media content).Controller 180 may simply request advertisements from the server andthen render whatever advertisements are received in response to therequest, or alternatively controller 180 may select the advertisementsto be rendered from a group of advertisements. This selection processcan be based on any of a wide range of criteria, such as randomselection, selecting the next advertisement in accordance with somepre-arranged ordering, attempting to identify (e.g., based on userpreferences or viewing characteristics) which advertisements are mostlikely to be of interest to the viewer, etc.

Advertisement controller 180 can optionally track advertisementrendering over multiple rendering sessions of the media content. Arendering session refers to the range between beginning playback (e.g.,by pressing a play button) and terminating playback (e.g., by pressing astop button, a quit or exit button, etc.). Advertisement controller 180can maintain a record (either locally or on a remote server) of the timesince the last advertisement even after playback is terminated. Ifplayback of the same media content (or a different version of that mediacontent) is again begun, then controller 180 begins counting time sincethe last advertisement from the stored value. Using this stored valuecan be absolute (e.g., regardless of where in the media content the userbegins playback), or alternatively variable (e.g., reset to zero or halfof the stored value if the user begins playing the media content fromthe beginning again rather than from where he or she previously leftoft). For example, assume a user begins watching a movie and thethreshold amount of time identifies that an advertisement should occurevery fifteen minutes. If the user watches ten minutes of the movie andthen stops playback, this time since the last advertisement (tenminutes) is stored by controller 180. If the user later begins watchingthe movie again (e.g., later that day, the next week, etc.), thencontroller 180 uses the value of ten minutes as the time since the lastadvertisement, so that five minutes after the user begins this secondplayback of the movie he or she will be presented with anadvertisement(s) because the total elapsed time has been fifteenminutes.

The counter of the time since the last advertisement can indicate anabsolute point where an advertisement should be rendered (e.g., simplystop rendering the current content at that point and render anadvertisement instead). Alternatively, when the timer elapses a moreintelligent approach may be taken to determining exactly when to renderan advertisement. In one implementation, the meta data associated withthe media content includes multiple advertisement preference points(e.g., indicated by the broadcaster or author of the content). After thetimer elapses (or alternatively starting an amount of time prior to thetimer elapsing), controller 180 stops rendering the current content whenthe next preference point is reached and renders an advertisement(s)instead. The frequency of these preference points can vary by content aswell as within content. For example, certain portions of the content mayhave preference points identified for every 30-second portion, whileother portions may have preference points identified for every 60-secondportion.

Various modifications can also optionally be included in client system102 for rendering advertisements. In one implementation, multipledifferent forms of the media content are available from the same ordifferent sources. These different forms vary in the number ofadvertisements—one form may have lots of advertisements, another formmay have a few advertisements, and another form may have noadvertisements. Which form the user views can be selected by the userand can vary based on the amount the user pays to view the content. Forexample, a user who pays a little bit may be able to view the form witha few advertisements, while a user paying more would be able to view theform with no advertisements, and a user paying nothing would be able toview the form with lots of advertisements. Access to particular formscan be restricted to only those users who pay the requisite amount in avariety of manners, such as a password system, by passing a decryptionkey to client systems 102 of users who pay the requisite amount so thatthe systems 102 can decrypt the encrypted content, etc.

Additionally, controller 180 may modify the threshold amount of timethat should occur between commercials based on the manner in which themedia content is rendered. In some situations, client system 102 mayallow for the playback of the media content to be slowed down or speededup (e.g., a user may select to playback the multimedia content at aspeed 25% faster than the “normal” playback speed and thus playback thecontent in a shorter amount of time). In such situations, controller 180correspondingly alters the threshold amount of time (e.g., reduce theamount of time that should occur between commercials by 25%).

Alternatively, advertisement controller 180 may employ different methodsto ensure that commercials are rendered by client system 102. By way ofexample, controller 180 may communicate with other components in clientsystem 102 to ensure that skip or fast forward controls are notoperational during commercials. This can be accomplished, for example,by communicating with a user interface component to identify when theuser interface component should accept the skip or fast forward inputs.The user interface component would then simply ignore any skip or fastforward inputs until informed by controller 180 that it is once againacceptable to receive skip or fast forward inputs.

Various additional modifications can be made to these advertisingmethods. For example, the frequency of advertisements can vary fordifferent media content (e.g., advertisements may occur every fifteenminutes for one movie but only every thirty minutes for another move).Additionally, the time and/or day of the viewing of the media contentmay alter the frequency and/or number of advertisements (e.g.,advertisements may occur more frequently during evening hours thanduring morning hours, or certain days may be “free” days during which noadvertisements are rendered).

Furthermore, a point system may be established in which a useraccumulates points for watching an advertisement. The number of pointsper advertisement can vary (e.g., based on a perceived importance to theadvertiser, based on the length of the advertisement, based on the timeof day or the day that the advertisement is rendered, based on the mediacontent corresponding to the advertisement, etc.). Accumulated pointscan then be “redeemed” in a variety of different manners (e.g., inexchange for certain goods and/or services, such as rendering of anadvertisement-free movie).

FIG. 8 is a flowchart illustrating an exemplary process for renderingadvertisements in accordance with certain embodiments of the invention.The process of FIG. 8 is carried out by a client system 102, and may beimplemented in software.

Initially, a check is made as to whether advertisements are to beincluded in the media content being rendered (act 320). Advertisementsmay not be included, for example, if the user has paid the requisitefee, has accumulated enough points, if it is a “free” day, etc. If thereare not to be any advertisements included in the media content, then noadvertisements are rendered (act 322). However, if there areadvertisements to be rendered, advertisement viewing parameters areidentified (act 324). The advertisement viewing parameters identify, forexample, a threshold amount of time that should not be exceeded betweenadvertisements. A check is then made as to whether it is time for anadvertisement, based on whether the threshold amount of time since thelast advertisement has elapsed (act 326). When it is time for anadvertisement, the system selects and renders an advertisement (act328), resets the time since last advertisement counter (act 330), andreturns to check whether it is time for an advertisement (act 326).

FIG. 9 illustrates an example of a suitable operating environment inwhich the invention may be implemented. The illustrated operatingenvironment is only one example of a suitable operating environment andis not intended to suggest any limitation as to the scope of use orfunctionality of the invention. Other well known computing systems,environments, and/or configurations that may be suitable for use withthe invention include, but are not limited to, personal computers,server computers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, programmable consumer electronics (e.g.,digital video recorders), Internet appliances, gaming consoles, cellulartelephones, network PCs, minicomputers, mainframe computers, distributedcomputing environments that include any of the above systems or devices,and the like.

FIG. 9 shows a general example of a computer 342 that can be used inaccordance with the invention. Computer 342 is shown as an example of acomputer in which various embodiments of the invention can be practiced,and can be, for example, a client 102 of FIG. 1 or one of servers 102,122, 126, 128, or 130 of FIG. 1. Computer 342 includes one or moreprocessors or processing units 344, a system memory 346, and a bus 348that couples various system components including the system memory 346to processors 344.

The bus 348 represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. The system memory 346 includesread only memory (ROM) 350 and random access memory (RAM) 352. A basicinput/output system (BIOS) 354, containing the basic routines that helpto transfer information between elements within computer 342, such asduring start-up, is stored in ROM 350. Computer 342 further includes ahard disk drive 356 for reading from and writing to a hard disk, notshown, connected to bus 348 via a hard disk drive interface 357 (e.g., aSCSI, ATA, or other type of interface); a magnetic disk drive 358 forreading from and writing to a removable magnetic disk 360, connected tobus 348 via a magnetic disk drive interface 361; and an optical diskdrive 362 for reading from and/or writing to a removable optical disk364 such as a CD ROM, DVD, or other optical media, connected to bus 348via an optical drive interface 365. The drives and their associatedcomputer-readable media provide nonvolatile storage of computer readableinstructions, data structures, program modules and other data forcomputer 342. Although the exemplary environment described hereinemploys a hard disk, a removable magnetic disk 360 and a removableoptical disk 364, it will be appreciated by those skilled in the artthat other types of computer readable media which can store data that isaccessible by a computer, such as magnetic cassettes, flash memorycards, random access memories (RAMs), read only memories (ROM), and thelike, may also be used in the exemplary operating environment.

A number of program modules may be stored on the hard disk, magneticdisk 360, optical disk 364, ROM 350, or RAM 352, including an operatingsystem 370, one or more application programs 372, other program modules374, and program data 376. A user may enter commands and informationinto computer 342 through input devices such as keyboard 378 andpointing device 380. Other input devices (not shown) may include amicrophone, joystick, game pad, satellite dish, scanner, or the like.These and other input devices are connected to the processing unit 344through an interface 368 that is coupled to the system bus (e.g., aserial port interface, a parallel port interface, a universal serial bus(USB) interface, etc.). A monitor 384 or other type of display device isalso connected to the system bus 348 via an interface, such as a videoadapter 386. In addition to the monitor, personal computers typicallyinclude other peripheral output devices (not shown) such as speakers andprinters.

Computer 342 operates in a networked environment using logicalconnections to one or more remote computers, such as a remote computer388. The remote computer 388 may be another personal computer, a server,a router, a network PC, a peer device or other common network node, andtypically includes many or all of the elements described above relativeto computer 342, although only a memory storage device 390 has beenillustrated in FIG. 9. The logical connections depicted in FIG. 9include a local area network (LAN) 392 and a wide area network (WAN)394. Such networking environments are commonplace in offices,enterprise-wide computer networks, intranets, and the Internet. Incertain embodiments of the invention, computer 342 executes an InternetWeb browser program (which may optionally be integrated into theoperating system 370) such as the “Internet Explorer” Web browsermanufactured and distributed by Microsoft Corporation of Redmond, Wash.

When used in a LAN networking environment, computer 342 is connected tothe local network 392 through a network interface or adapter 396. Whenused in a WAN networking environment, computer 342 typically includes amodem 398 or other means for establishing communications over the widearea network 394, such as the Internet. The modem 398, which may beinternal or external, is connected to the system bus 348 via a serialport interface 368. In a networked environment, program modules depictedrelative to the personal computer 342, or portions thereof, may bestored in the remote memory storage device. It will be appreciated thatthe network connections shown are exemplary and other means ofestablishing a communications link between the computers may be used.

Computer 342 also includes a broadcast tuner 400. Broadcast tuner 400receives broadcast signals either directly (e.g., analog or digitalcable transmissions fed directly into tuner 400) or via a receptiondevice (e.g., via antenna or satellite dish).

Computer 342 typically includes at least some form of computer readablemedia. Computer readable media can be any available media that can beaccessed by computer 342. By way of example, and not limitation,computer readable media may comprise computer storage media andcommunication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other media whichcan be used to store the desired information and which can be accessedby computer 342. Communication media typically embodies computerreadable instructions, data structures, program modules or other data ina modulated data signal such as a carrier wave or other transportmechanism and includes any in formation delivery media. The term“modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media. Combinations of any of the above should also be includedwithin the scope of computer readable media.

The invention has been described in part in the general context ofcomputer-executable instructions, such as program modules, executed byone or more computers or other devices. Generally, program modulesinclude routines, programs, objects, components, data structures, etc.that perform particular tasks or implement particular abstract datatypes. Typically the functionality of the program modules may becombined or distributed as desired in various embodiments.

For purposes of illustration, programs and other executable programcomponents such as the operating system are illustrated herein asdiscrete blocks, although it is recognized that such programs andcomponents reside at various times in different storage components ofthe computer, and are executed by the data processor(s) of the computer.

Alternatively, the invention may be implemented in hardware or acombination of hardware, software, and/or firmware. For example, one ormore application specific integrated circuits (ASICs) could be designedor programmed to carry out the invention.

CONCLUSION

Although the description above uses language that is specific tostructural features and/or methodological acts, it is to be understoodthat the invention defined in the appended claims is not limited to thespecific features or acts described. Rather, the specific features andacts are disclosed as exemplary forms of implementing the invention.

1. A computer-readable storage device containing computer-executableinstructions for controlling a computing device to render portions of avideo, the video being previously recorded, by a method comprising:receiving meta data corresponding to the video that was previouslyrecorded, wherein the meta data includes comments and an identificationof portions within the video to which the comments apply; storing themeta data in association with the video that was previously recorded;and for each of the plurality of viewers, receiving from the viewerinput search criteria relating to the video; searching the stored metadata to identify comments of the meta data that satisfy the input searchcriteria; for each of a plurality of identified comments, selecting theportion of the video to which the identified comment applies asindicated by the received meta data; and sending the selection portionsof the media content for rendering to the viewer the selected portionsof the video without rendering the non-selected portions as a renderingthat is separate from the renderings for other viewers.
 2. Thecomputer-readable storage device of claim 1 wherein the rendering of theselected portions includes displaying comments that apply to therendered portions.
 3. The computer-readable storage device of claim 1wherein the receiving of the meta data includes receiving meta data frommultiple viewers viewing different versions of the video andconsolidating the meta data received from the multiple viewers into themeta data corresponding to the video.
 4. The computer-readable storagedevice of claim 3 wherein versions of the video include a livetelevision broadcast and recorded version of the television broadcast.5. The computer-readable storage device of claim 1 wherein the renderingincludes storing for subsequent rendering the selected portions of thevideo without storing the not selected portions of the video.
 6. Thecomputer-readable storage device of claim 1 wherein the meta datafurther includes an identification of a group of viewers who areauthorized to view the comments.
 7. The computer-readable storage deviceof claim 1 wherein the rendering include identifying an amount of timethat the selected portions of the video have been rendered and renderingan advertisement when the identified amount of time exceed a thresholdamount.
 8. The computer-readable storage device of claim 7 wherein thethreshold amount is based on a fee paid by the viewer viewing therendering of the selected portions.
 9. The computer-readable storagedevice of claim 1 including identifying a preference point of the videoat which an advertisement is to be rendered.
 10. A computing device forprocessing portions of media content, comprising: a data store storingmeta data corresponding to the media content, wherein the meta dataincludes comments and an identification of portions within the mediacontent to which the comments apply; a memory storingcomputer-executable instructions of: a component that, for each of aplurality input search criteria, searches the meta data to identifycomments of the meta data that satisfy the input search criteria; foreach identified comment, selects the portion of the media content towhich the identified comment applies as indicated by the stored metadata; and stores the selected portions of the media content on a storagedevice without storing the not selected portions so that the selectedportions are stored separately for each input search criteria; and aprocessor that executes the computer-executable instructions stored inthe memory.
 11. The computing device of claim 10 wherein each inputsearch criteria is input from a viewer and including rendering theselected portions of the media content to the viewer.
 12. The computingdevice of claim 11 wherein the rendering of the selected portionsincludes displaying comments that apply to the rendered portions. 13.The computing device of claim 10 including a component that receivesmeta data from multiple viewers viewing different versions of the mediacontent, consolidates the meta data received from the multiple viewersinto the meta data corresponding to the media content, and stores theconsolidated meta data in the data store.
 14. The computing device ofclaim 13 wherein the media content is video and versions of the videoinclude a live television broadcast and recorded version of thetelevision broadcast.
 15. The computing device of claim 10 wherein themeta data further includes an identification of a group of viewers whoare authorized to view a comment.
 16. A method performed by a computingdevice for rendering portions of media content, the media content beingstored on a storage device, the computing device having a processor anda memory, the method comprising: receiving meta data corresponding tothe media content stored on the storage device, wherein the meta dataincludes comments and an identification of portions within the mediacontent to which the comments apply; storing the received meta data inassociation with the media content stored on the storage device; and foreach of the plurality of viewers, receiving from the viewer input searchcriteria relating to the media content; searching by the computingdevice the meta data to identify comments of the meta data that satisfythe input search criteria; for each identified comment, selecting by thecomputing device the portion of the media content to which theidentified comment applies as indicated by the received meta data; andsending the selection portions of the media content for rendering to theviewer the selected portions of the media content as a rendering that isseparate from the renderings for other viewers.
 17. The method of claim16 wherein the rendering of the selected portions includes displayingcomments that apply to the rendered portions.
 18. The method of claim 16wherein the receiving of the meta data includes receiving meta data frommultiple viewers viewing different versions of the media content andconsolidating the meta data received from the multiple viewers into themeta data corresponding to the media content.
 19. The method of claim 16wherein the rendering includes storing for subsequent rendering theselected portions of the media content without storing the not selectedportions of the media content.
 20. The method of claim 16 wherein themeta data further includes an identification of a group of viewers whoare authorized to view a comment.